Troubleshooting

Version 1.2 Troubleshooting   New!

Applets created with version 1.2 require that the latest version of .cab and .class files be uploaded to your server.   If you see a message like "NumberFormatException: ^192" in your browser status bar, you need to upload the new .cab and .class files.

To fix the problem, follow this procedure:

  1. Clear the cache on all browsers you have installed.
  2. Close down any browsers you have running.
  3. Open your button project and rebuild it with version 1.2. (Make sure it works when you press "Test Applet in Browser")
  4. Upload the .class, .cab and HTML files to your web server.
  5. Restart your browser and test the applet over the internet
Installation Problems:

The most common problem when installing 1 Cool Button Tool is a broken Java Virtual Machine (JVM).   If your JVM is not working, the application will report that BtnPlayer.class is not in the same folder as the executable (1cool.exe).

To fix this problem you will need to install an new JVM.

If you have Internet Explorer 3.01 (or earlier) installed, you should download and install IE 3.02 or IE 4.x from the Microsoft Site.

If you already have IE3.02 (or later) installed, follow the procedure below:
  1. Restart Internet Explorer (very important).

  2. Using Internet Explorer, go to the Download JVM page.

  3. Follow the instructions at the Microsoft site, and wait while IE "installs components". (This can take quite a while)

  4. Restart your machine and launch 1 Cool Button Tool.

Troubleshooting Applets:

If you are having difficulties getting your button applet running over the internet, here are some quick tips:
  • Button applets are comprised of the following files; an HTML file, BtnPlayer.class, a .cab file and any bitmap and sound files used by the applet.

    All these files must be in the same folder on your web server.

  • .class files and .cab files are binary files. If you are using FTP to copy your applet the web server, you should copy these files in binary mode.

  • Button applets built with the unregistered version of 1 Cool Button Tool will not run over the internet. When you build an applet with the registered version it will write an "r" parameter into the applet code which "unlocks" the applet so it run run over the internet.

    You should re-build any applets you want to run over the internet with the registered version.

  • Do not edit any of the applet parameters in the HTML code.   Changing any applet parameters will make the "r" parameter value incorrect and the applet will not run over the internet.

  • If your applet shows only a gray box, move the cursor over the applet area and look at the status bar of your browser.   The status bar will contain information about why the applet is not working.

    For example, the status bar might read "Load: class BtnPlayer not found" which means you have not copied the BtnPlayer.class file to your web server.

  • If you want more information about why your applet is not running, you can look at the Java Log.   On Netscape, the java log written to the "Java Console" (Options->Java Console). Internet Explorer writes the java log to a file called "javalog.txt" in your Windows directory, typically \windows\java\javalog.txt

Common Applet Problems:

When I run my applet in a browser all I see is a gray box.

Move the cursor over the applet area and look at the status bar of your browser.
The status bar will contain information about why the applet is not working.

  • The status bar reads: Load: class BtnPlayer not found or Applet can't start: class BtnPlayer not found

     The BtnPlayer.class file is not in the same directory as the HTML file.
  • The status bar reads: java.lang.ClassFormatError or says something about the class file format being incorrect.

     The BtnPlayer.class file is corrupted.   The most common reason for this is that the file was FTP'ed to the web server in ASCII mode.   .class files are binary files and must be FTP'ed in BINARY mode.
  • The status bar reads: exception: com.ms.applet.CabLoaderException: Cabinet file not found (occurs in Internet Explorer only).

     The BtnPlayer.cab file is not in the same directory as the HTML file.
  • The status bar reads: exception: com.ms.applet.CabLoaderException: Corrupt Cabinet file (occurs in Internet Explorer only).

     The BtnPlayer.cab file is corrupted.   The most common reason for this is that the file was FTP'ed to the web server in ASCII mode.   .cab files are binary files and must be FTP'ed in BINARY mode.
  • The status bar reads: com.ms.applet.AppletSecurityException (occurs in Internet Explorer 3.0.2 only).

     This is a bug in Internet Explorer 3.02 which prevents Java Applets from reading bitmap and sound files from your hard drive.

    Microsoft have released a fix for this bug which is available at: http://www.microsoft.com/java/vm/dl_vmsp2.htm

    This problem does not affect Java Applets run over the internet, so it does not affect visitors to your site.

When I run my applet over the internet I see an |UNREGISTERED| message in the center of the applet

Possible Causes:
  1. The applet has been built with an unregistered version of 1 Cool Button Tool.   The registered version will write an "r" parameter in the applet code which "unlocks" the applet so it can run over the internet.

  2. This error can also occur if you edit any of the applet parameters after the applet code has been pasted into the HTML file.   Changing any applet parameters will make the "r" parameter value incorrect and the applet will not run over the internet.

My bitmaps don't display and/or my sounds don't play

Possible Causes:
  1. Some proxy servers do not allow Java applets to read files.   Ask your system administrator if this is the case.

  2. Java applets are case sensitive so "bitmap.jpg" and "Bitmap.JPG" are treated as different files.   If your button applet is trying to read "bitmap.jpg" but the only file on the server is "Bitmap.JPG", your bitmap will not appear.

    (Note: Some versions of Photoshop capitalize the extension when you save the file.)

  3. Netscape 3 (and earlier) has problems reading some JPEG files, particularly progressive JPEGs. If your applet runs fine in IE but not in Netscape, open your Java Console (Options->Java Console) and look for errors relating to reading images.   To fix this error you will need to open and re-save the offending JPEG files with another bitmap editor.   (JPEGs saved using Paint Shop Pro seem to be ok)

If your question is not anwsered here email: 1coolsupport@formulagraphics.com.